Systems and methods for a marketplace of interactive live streaming multimedia overlays

ABSTRACT

This present disclosure described methods for a marketplace of interactive live streaming multimedia overlays. At least one method includes a user playing video games on a computer, using software to stream all or part of their computer session to one or more streaming services, said software retrieving images from a web-service, some or all of said images having been acquired through an online marketplace, said images being used to create a video overlay, and said overlay being combined with the video of the user&#39;s computer session prior being encoded for transmission to one or more streaming services.

FIELD OF THE DISCLOSURE

The present disclosure relates to marketplace of interactive livestreaming multimedia overlays.

BACKGROUND

This present disclosure relates to methods for a marketplace ofinteractive live streaming multimedia overlays.

The online video industry has grown rapidly since YouTube made it simpleto share online videos in 2005. Netflix introduced its streaming videoservice in 2007, followed by Hulu in 2008. All three services focused onpre-recorded video, also known as Video On Demand (“VOD”), until YouTubeintroduced YouTube Live in 2008. It marked the first easily accessibleimplementation of a live streaming video service.

Similarly, video games have evolved from single or multiplayerexperiences shared around a single TV to complicated, internet-basedmultiplayer games that allow hundreds of thousands of players toparticipate in shared gaming experiences. Fans of video gameshistorically used magazines such as GamePro Magazine to stay abreast ofnew game releases, uncover otherwise difficult to find game secrets, andto learn how optimize their gameplay. Eventually the medium was replacedby YouTube channels dedicated to video game content.

The popularity of online video game content lead to the founding of anew class of Streaming Services: Twitch, which was founded in 2011, andYouTube Gaming which came online in 2015. These services allowed playersto directly broadcast their own gaming experiences to the world.Streaming Services differ from the aforementioned Netflix, Hulu, andYouTube products in that they focus on streaming live video, as opposedto pre-recorded VOD content. Today Twitch serves over 170 millionvisitors every month, and unlike YouTube's VOD product, which primarilyserves short-form video, the average Twitch visitor views over an hourof streaming content. For the purpose of the present invention, the termStreaming Services refers to one or more services designed to streamlive video content via a digital channel including, but not limited to,Twitch, YouTube Gaming, Mixer, and Facebook Live.

These extended viewing times are enabled by video game fans' voraciousappetite for video game content, and by Streaming Services such asTwitch or YouTube Gaming providing tools to enable users broadcastingtheir games, the Streamers, to monetize the time they spend streamingtheir game sessions. These tools include allowing Viewers to sign up fora monthly subscription to the channel of a specific Streamers whosepersonality or gameplay they enjoy, a chat panel for viewers to chatwith each other and the Streamer, and an extensive applicationprogramming interface (API) for developers to build applications thatinterface with the Streaming Services. Many Streamers are able to make asubstantial living through Streaming Services and the ecosystems theyhave created.

Due to the instantaneous and live nature of video streamed to StreamingServices, it is not possible to edit a video before it goes live usingtraditional video editing software. To overcome this limitationbroadcasting software, such as Open Broadcaster Software (“OBS”), hasintroduced the ability to use Overlays, which are graphical elementsthat are added to the Streamer's video immediately prior to the videobeing encoded and sent to Streaming Services for Viewer consumption.Overlays can consist of static or dynamic images, and they can be storedlocally or hosted on a server.

Furthermore, Streaming Service APIs have created an ecosystem ofthird-party tools that help Streamers monetize their channels beyondViewer subscriptions. Key features developed by third party servicesinclude facilitating donations (a primary source of income forStreamers), Multistreaming Services that broadcast a single Streamer'svideo feed to multiple simultaneous Streaming Services, chat bots thathelp Streamers engage with and manage their Viewers through the chatpane, and custom Overlays. Said custom Overlays can provide staticimages, such as decorative video borders, animated graphics that respondin real time to the actions of the Viewers or the game.

An example of a real-time alert includes an animated alert appearing inthe Streamer's video feed when a Viewer subscribes, follows, or donatesto the Streamer. This allows the Streamer to easily see Viewermonetization events as they occur. It also gives the Viewer a chance atnotoriety as their name is displayed in front of potentially millions ofother Viewers.

Another example of a real-time alert is a widget system that allows theStreamer to display the chat pane contents directly within the videofeed. This allows the Streamer to monitor both the output of their livestream and their Viewer conversations in one place, without having tomanually show and hide the chat panel while they are live. These andother alert examples have become integral to the success of StreamingServices, and Viewers have come to expect them from their favoriteStreamers.

Graphics for custom Overlays heretofore were provided either by the enduser as local files or as preset templates hosted on a server by thethird-party service. The templates can be customized into an almostinfinite array of configurations. Additionally, Streamers often preferto have different Overlay configurations for different games, asdifferent games produce different graphical looks and feels thatcoordinate best with different Overlay settings. For these reasons,Overlay configurations often require considerable time, effort, andpotentially some technical know-how to produce, all of which take awayfrom time the Streamer could instead dedicate to monetizing theirchannel.

Alternatively, a Streamer can hire a graphic designer to produce customOverlays for their channel. This usually requires a specialty in videogame design or animation, very specific understanding of the market,potentially access to the Streamer's account on the third-party service,and knowledge of how to operate the third-party systems. This alsorequires an interested Streamer and designer to connect via job ads,referrals, or coincidence; while each of the aforementioned methods arevalid, they do not provide a distribution channel through whichdesigners can publish Overlay graphics for potential monetization, nordo they streamline the browsing, acquisition, and consumption of Overlaygraphics by Streamers.

SUMMARY

Presently disclosed is a method for a marketplace of interactive livestreaming multimedia overlays. In embodiments, the method includes aserver infrastructure configured to permit a plurality of users toupload and store graphics and/or audio and overlay configurationinformation for a given video overlay, where said configurationinformation specifies values for one or more settings that define theapplication of the image and/or audio of the given video overlay, saidinfrastructure being configured to transmit to client computingplatforms associated with users information that facilitatespresentation of views of a marketplace, said graphics being selectableby one or more users, where a copy of the selected graphics are madeavailable to a second user ; providing a video overlay hosted on theserver infrastructure, said overlay being configured to incorporategraphics; said second user adding one or more of said graphics to theoverlay configuration; the second user saving the overlay configuration;server infrastructure configured to receive the second user's acceptanceof said graphics and the second user's overlay configuration; serverinfrastructure producing an image file based on the overlayconfiguration then providing the client computing platforms associatedwith the second user access to the corresponding video overlays;broadcasting software operated by the second user retrieving the overlayimage from the server; the broadcasting software encoding video outputfrom the second user's computer and the overlay image to produce a videofile; uploading the encoded video file to a streaming service; thestreaming service decoding the video file; the streaming servicedisplaying the video file for consumption by a plurality of users.

In some embodiments, the server infrastructure is configured tofacilitate the designing, editing, and animating of the graphics.

In some embodiments, the broadcasting software encodes the output of theuser's local webcam with the overlay and the video feed.

In some embodiments, the broadcasting software is operated from aself-contained mobile computer, such as a smartphone, augmented realityequipment, or virtual reality equipment.

In some embodiments, the broadcasting software combines media outputsfrom multiple computers to produce the encoded video file.

In some embodiments, the second user can edit the copy of the graphicsthey have selected before the graphics are added to the overlay.

In some embodiments, the graphics are offered for sale.

In some embodiments, multiple graphics are organized into templates.

In some embodiments, the graphics or templates are grouped for browsingby specific content types.

In some embodiments, the graphics are static images.

In some embodiments, the video overlay is applied to other video contentas a filter.

In some embodiments, the graphics are dynamic images, which are added tothe overlay image file in a predetermined sequence over consecutiveframes to generate an animation.

In some embodiments, the selected graphics are initiated at random timeintervals, where an algorithm randomly selects intervals in which todisplay the selected graphics.

In some embodiments, the selected graphics are initiated atpredetermined intervals, where a timer is configured by either the firstor the second user to display the selected graphics at said configuredintervals.

In some embodiments, the overlay configuration specifies the position,duration, and/or real-time event trigger for determining when the imageand/or audio of the given video overlay is applied.

Also disclosed is a method for a marketplace of interactive livestreaming multimedia overlays that includes a server infrastructureconfigured to permit a plurality of users to upload and store graphicsand/or audio and overlay configuration information for a given videooverlay, where said configuration information specifies values for oneor more settings that define the application of the image and/or audioof the given video overlay, said infrastructure being configured totransmit to client computing platforms associated with users informationthat facilitates presentation of views of a marketplace, said graphicsbeing selectable by one or more users; providing a video overlay hostedon the server infrastructure, said overlay being configured toincorporate graphics; the server infrastructure configured to receivedata from a data API; the graphics configured by a first user to respondto one or more predefined API data events; a second user adding one ormore of said graphics to the overlay configuration; the second usersaving the overlay configuration; server infrastructure configured toreceive the second user's acceptance of said graphics and the seconduser's overlay configuration; the server infrastructure producing anoverlay image file including said graphics in response to the predefinedAPI data events then providing the client computing platforms associatedwith the second user access to the corresponding video overlays;broadcasting software operated by the second user retrieving the overlayimage from the server; the broadcasting software encoding video outputfrom the second user's computer and the overlay image to produce a videofile; uploading the encoded video file to a streaming service; thestreaming service decoding the video file; the streaming servicedisplaying the video file for consumption by a plurality of users.

In some embodiments, the API data is received from multiple data APIsources.

In some embodiments, some or all API data is received from a programoperating on the second user's local computer, such as the user's videogame program.

In some embodiments, some or all API data is received from a computervision program or artificial intelligence engine operating on the seconduser's computer.

In some embodiments, some or all API data is received from a computervision program or artificial intelligence engine operating in the serverinfrastructure.

In some embodiments, some or all API data is received from a computervision program or artificial intelligence engine operating in themultistream service.

Also disclosed is a method for a marketplace of interactive livestreaming multimedia overlays that includes a server infrastructureconfigured to permit a plurality of users to upload and store graphicsand/or audio and overlay configuration information for a given videooverlay, where said configuration information specifies values for oneor more settings that define the application of the image and/or audioof the given video overlay, said infrastructure being configured totransmit to client computing platforms associated with users informationthat facilitates presentation of views of a marketplace, said graphicsbeing selectable by one or more users; providing a video overlay hostedon the server infrastructure, said overlay being configured toincorporate graphics; the server infrastructure configured to receivedata from a data API; the graphics configured by the first user torespond to one or more predefined API data events; a second user addingone or more of said graphics to the overlay configuration; the seconduser saving the overlay configuration; server infrastructure configuredto receive the second user's acceptance of said graphics and the seconduser's overlay configuration; the server infrastructure producing anoverlay image file including said graphics in response to the predefinedAPI data events then providing the client computing platforms associatedwith the second user access to the corresponding video overlays;broadcasting software operated by the second user retrieving the overlayimage from the server infrastructure; the broadcasting software encodingvideo output from the second user's computer and the overlay image toproduce an encoded video file prior to transmission to a third serverfor broadcasting; uploading the encoded output of the overlay and videoto a multistream service, which is configured to upload the encodedvideo file to one or more streaming services; the streaming servicesthen decode the video file and display the video file for consumption bya plurality of users.

In some embodiments, the multistream service decodes the encoded videofile, then encodes the video in formats suitable to one or morestreaming services, then uploads the encoded outputs to eachcorresponding streaming service; the streaming services then decode thevideo file and display the video for consumption by a plurality ofusers.

In some embodiments, API data is received from multiple data APIsources; one or more data sources are designated to create graphicsspecific to one or more video streaming services; said graphics are usedto create one or more overlay; the encoded output of the video and eachoverlay are then uploaded to a multistream service, which uploads one ormore corresponding encoded outputs to one or more correspondingstreaming service.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the various disclosed embodiments can beobtained when the following detailed description is considered inconjunction with the attached drawings, in which:

FIG. 1 shows a system diagram that includes an illustrative WebInfrastructure.

FIG. 2 shows a system diagram that includes an illustrative WebInfrastructure with multiple data sources and multistreaminfrastructure.

FIG. 3 shows a software flowchart and functional method for populatingan overlay marketplace.

FIG. 4 shows a software flowchart and functional method for organizingoverlay images into a template.

FIG. 5 shows a software flowchart and functional method for purchasingoverlay images in a marketplace.

FIG. 6 shows a software flowchart of a system for configuring amultimedia overlay.

FIG. 7 shows a non-limiting example of a configured multimedia overlay.

FIG. 8 shows a software flowchart and functional distribution for afirst illustrative embodiment.

FIGS. 9A and 9B show a software flowchart and functional distributionfor a second illustrative embodiment.

FIGS. 10A and 10B show a software flowchart and functional distributionfor a third illustrative embodiment.

-   It should be understood that the drawings and corresponding detailed    description do not limit the disclosure, but on the contrary, they    provide the foundation for understanding all modifications,    equivalents, and alternatives falling within the scope of the    appended claims.

DETAILED DESCRIPTION Introduction

The disclosed embodiments relate to a marketplace for streamingmultimedia overlays for use with video games, movies, entertainmentmedia and/or other non-entertainment media. More specifically, thedisclosed embodiments relate to interconnected systems executingsoftware related to acquiring new graphics and animations for use in adynamically-generated, web-hosted streaming video overlay.

The disclosed embodiments rely on a live video streaming architecture,where part of the stream includes inserting a graphical overlay prior toencoding the video for distribution. The first user in these embodimentsprovides custom graphics to the marketplace. The second user (e.g. the“streamer”) selects and configures from among the graphics in themarketplace those that will be generated into a video overlay in realtime based on timers, specific events, or data received from third partydata sources. The second user then configures local broadcast softwareto combine two or more separate data sources into an encoded video: aspecific application or video game signal; the internet-hosted videooverlay, which is generated by the server infrastructure at regularintervals to potentially give the appearance that it is animated andsynchronized to current events in the application or video game signal;and optionally the second user's local camera feed, which, whenincluded, may allow viewers to see the second user as they are usingtheir application or playing a video game. The aforementioned signalsare then encoded by the user's local broadcast software for upload toone or more streaming websites, such as Twitch, YouTube Gaming, Mixer,or Facebook Live.

Given that video overlays are integral to the monetization of astreamer's channel, and given that streamers usually receive donationsand subscriptions while they are streaming, it is in their best interestto minimize the time they spend managing and customizing their videooverlay.

In contrast to prior systems, a user-generated marketplace for graphicsand animations used in dynamic multimedia overlays makes it seamless forstreamers to discover and try new video overlay designs to find whatworks best for their viewers. Because the designs are uploaded by aplurality of users, the range and variety of potential designs willscale with greater ease when compared to prior systems, where designsare provided by a single company. Furthermore, the disclosed embodimentsenable a new channel through which designers can seamlessly create,edit, market, monetize, and distribute custom graphics and animationsused in streaming video overlays directly to the users of said overlays.Designers are incentivized to participate in the marketplace through thepotential to have their work seen by tens of thousands of viewers andthe potential to monetize their work. This flexibility and scalabilitywas not possible with prior systems, such as those discussed above, inwhich these transactions occurred in private and relied on individualsconnecting through research or happenstance.

The paragraphs that follow describe in detail various examples of theabove-described embodiments. An example of an illustrative Webinfrastructure is described, followed by an illustrative Webinfrastructure utilizing dynamic data and multi-streaminginfrastructure. The individual use-cases that complete the system (i.e.,populating the marketplace, optionally organizing images into atemplate, purchasing a graphic or template, and using images toconfigure an overlay) are then described through software flowcharts. Anon-limiting illustrative example of a configured overlay is thenprovided. Finally three illustrative embodiments are described, whereinthe video overlay might be static or dynamic, the data sources may beone or many, and the broadcasting architecture may be direct or includemulticast infrastructure.

Web Infrastructure

FIG. 1 shows an overview of an illustrative embodiment of a marketplaceof interactive live streaming multimedia overlays that includes a ServerInfrastructure 100, an Internet 120 infrastructure, a Local Computer 230operating a Local Broadcast Software 240, a Streaming Service 150,Viewers 170, a method for collecting Viewer Interactions 160, and aStreaming Service API 130. The Server Infrastructure 100 contains amethod for persistent storage, such as a database, as well as a methodfor initiating and responding to internet requests, such as a webserver. The Server Infrastructure 100 stores and makes various usersettings available for retrieval, including the user's OverlayConfiguration 110.

The Local Computer 230 may be a traditional desktop computer, a laptop,a mobile phone, a virtual or augmented reality computing device, or anyrelated personal computing device. The Streaming Service API 130connection may be unidirectional or bilateral. The Streaming Service API130 may also be a RESTful service, a persistent websockets connection,or any other method of regularly publishing and sharing informationbetween disparate internet systems. The Game Signal 220 includes, but isnot limited to, an audio/video signal from a videogame, a specificapplication unrelated to a videogame, or the user's operating systemenvironment including some or all applications the user has executed.Multiple Game Signals 220 and User Signals 210 may also be combined tocreate the Game Signal 220 or User Signal 210.

In the embodiment shown, the Server Infrastructure 100 responds torequests from the Local Broadcast Software 240 executing on the LocalComputer 230, and further retrieves the Overlay Configuration 110 asneeded. The Local Software may be stored on a non-volatile informationmedium, or it may be downloaded onto the Local Computer 230 via, e.g.,the Internet 120.

The core functionalities of the Server Infrastructure 100 include, butare not limited to:

1. Responding to requests from the Local Broadcast Software 240, LocalComputer 230, or Streaming Service API 130;

2. Hosting the marketplace from which the user selects the graphics thatcomprise the user's Overlay Configuration 110;

3. Hosting a web page that allows users to edit their OverlayConfiguration 110;

4. Initiating and maintaining persistent connections with the StreamingService API 140;

5. Generating the Graphical Overlay 200 based on the user's OverlayConfiguration 110 at set intervals, based on specific data events, uponrequest, or otherwise as needed;

6. Maintaining User account information; and

7. Hosting and web sites required to support the disclosed system.

The core functionalities of the Local Broadcast Software 240 include,but are not limited to:

1. Receiving a Game Signal 220 and, optionally, a User Signal 210 fromthe Local Computer 230;

2. Using the Internet 120 to retrieve the Graphical Overlay 200 from theServer Infrastructure 100;

3. Using the Video Encoder 190 to produce a video file from the GameSignal 220, the optional User Signal 210, and the Graphical Overlay 200;

4. Sending authentication information to the Streaming Service 150 toidentify the user uploading the video file;

5. Uploading the video file to a Multistream Service 250 using StreamingProtocols 180;

6. Storing user settings related to, but not limited to:

-   -   a. Streaming Services 150 the user may broadcast their encoded        video file;    -   b. Encoding settings used to configure and optimize the Video        Encoder 190; and    -   c. Streaming settings used to configure and optimize the        Streaming Protocols 180 used to upload the video file to        Streaming Service 150.

The core functionalities of the Streaming Service 150 include, but arenot limited to:

1. Storing account details for the user;

2. Receiving authentication information from the Local BroadcastSoftware 240;

3. Using the authentication information to identify the user uploadingthe video file;

4. Receiving the uploaded video file from the Local Broadcast Software240 via a Streaming Protocol 180;

5. Decoding the video file;

6. Playing the decoded video file for Viewers 170 to consume on theuser's channel;

7. Gathering metadata about Viewer Interactions 160 including, but notlimited to:

-   -   a. The type of interaction;    -   b. The time of the interaction;    -   c. The Viewer's 170 account details; and

8. Storing Viewer Interactions 160 for retrieval by the StreamingService API 130.

The core functionalities of the Streaming Service API 130 include, butare not limited to:

1. Retrieving Viewer Interactions 160 for processing;

2. Processing Viewer Interactions 160 into Stream Events 140 formattedfor use in the Streaming Service API 130;

3. Sending the Stream Events 140 to the connected Server Infrastructure100 via the Streaming Service API 130.

Web Infrastructure With Multiple Data Sources and MultistreaminqInfrastructure

FIG. 2 shows an overview of an illustrative embodiment of a marketplaceof interactive live streaming multimedia overlays that includes theServer Infrastructure 100, an Internet 120 infrastructure, a LocalComputer 230 operating Local Broadcast Software 240, a MultistreamService 250, a Streaming Service 150, Viewers 170, a method forcollecting Viewer Interactions 160, and one or more Streaming ServiceAPI(s) 130. The Server Infrastructure 100 contains a method forpersistent storage, such as a database, as well as a method forinitiating and responding to internet requests, such as a web server.The Server Infrastructure 100 stores and makes various user settingsavailable for retrieval, including the user's Overlay Configuration 110.This embodiment potentially includes Alternative API Data Sources 270,which are data sources unrelated to the Streaming Service API(s) 130that are used in the creation of the Graphical Overlay 200. Thisembodiment of the Server Infrastructure 100 contains an API DataCollector 260, which is responsible for aggregating data from one ormore Streaming Service API(s) 130 and Alternative API Data Sources 270.Data gathered by the API Data Collector 260 is then used in combinationwith the user's Overlay Configuration 110 to populate the GraphicalOverlay 200. While not depicted in this embodiment, the Alternative APIData Sources 270 may also be generated by a local program executing onthe user's computer.

The Local Computer 230 may be a traditional desktop computer, a laptop,a mobile phone, a virtual or augmented reality computing device, or anyrelated personal computing device. The Streaming Service API(s) 130 andthe Alternative API Data Sources 270 connection(s) may be unidirectionalor bilateral. The Streaming Service API(s) 130 and the Alternative APIData Sources 270 may also be a RESTful service, a persistent websocketsconnection, or any other method of regularly publishing and sharinginformation between disparate internet systems. The Game Signal 220includes, but is not limited to, an audio/video signal from a videogame,a specific application unrelated to a videogame, or the user's operatingsystem environment including some or all applications the user hasexecuted. Multiple Game Signals 220 and User Signals 210 may also becombined to create the Game Signal 220 or User Signal 210.

In the embodiment shown, the Server Infrastructure 100 responds torequests from the Local Broadcast Software 240 executing on the LocalComputer 230, and further retrieves the Overlay Configuration 110 asneeded. The Local Software may be stored on a non-volatile informationmedium, or it may be downloaded onto the Local Computer 230 via, e.g.,the Internet 120.

The core functionalities of the Server Infrastructure 100 include, butare not limited to:

1. Responding to requests from the Local Broadcast Software 240, LocalComputer 230, or Streaming Service API 130;

2. Hosting the marketplace from which the user selects the graphics thatcomprise the user's Overlay Configuration 110;

3. Hosting a web page that allows users to edit their OverlayConfiguration 110;

4. Executing the API Data Collector 260, which may perform, but is notlimited to, the following actions:

-   -   a. Maintains persistent connections with the Streaming Service        API(s) 130;    -   b. Receives data from Alternative API Data Sources 270;    -   c. Stores metadata about the data received from the Streaming        Service API(s) 130 and Alternative API Data Sources 270;    -   d. Stores data aggregated from one or more source related to the        user in the user's account;

5. Generating the Graphical Overlay 200 based on the user's OverlayConfiguration 110 at set intervals, based on specific data events asthey are received in real time by the API Data Collector 260, uponrequest, or otherwise as needed;

6. Maintaining user account information;

7. Hosting the Multistream Service 250; and

8. Hosting and web sites required to support the disclosed system.

The core functionalities of the Local Broadcast Software 240 include,but are not limited to:

1. Receiving a Game Signal 220 and, optionally, a User Signal 210 fromthe Local Computer 230;

2. Using the Internet 120 to retrieve the Graphical Overlay 200 from theServer Infrastructure 100;

3. Using the Video Encoder 190 to produce a video file from the GameSignal 220, the optional User Signal 210, and the Graphical Overlay 200;

4. Sending authentication information to the Streaming Service 150 toidentify the user uploading the video file;

5. Uploading the video file to a Multistream Service 250 using StreamingProtocols 180;

6. Storing user settings related to, but not limited to:

-   -   a. Streaming Services 150 the user may broadcast their encoded        video file;    -   b. Encoding settings used to configure and optimize the Video        Encoder 190; and    -   c. Streaming settings used to configure and optimize the        Streaming Protocols 180 used to upload the video file to        Streaming Service 150.

The core functionalities of the Multistream Service 250 include, but arenot limited to:

1. Storing user configuration settings to control which StreamingService(s) 150 an uploaded video file should be redistributed to;

2. Optionally receiving authentication information from the LocalBroadcast Software 240;

3. If authentication information is received, forwarding saidauthentication information to one or more Streaming Services 150;

4. Receiving the uploaded video file from the Local Broadcast Service240 via a Streaming Protocol 180;

5. Optionally decoding the video file, then re-encoding the file tooptimize it for individual Streaming Service(s) 150; or

6. Uploading the video file to one or more Streaming Service 150 using aStreaming Protocol 180.

The core functionalities of each of the Streaming Service(s) 150include, but are not limited to:

1. Storing account details for the user;

2. Receiving authentication information from the Local BroadcastSoftware 240 and/or the Multistream Service 250;

3. Using the authentication information to identify the user uploadingthe video file;

4. Receiving the uploaded video file from the Multistream Service 250via a Streaming Protocol 180;

5. Decoding the video file;

6. Playing the decoded video file for Viewers 170 to consume on theuser's channel;

7. Gathering metadata about Viewer Interactions 160 including, but notlimited to:

-   -   a. The type of interaction;    -   b. The time of the interaction;    -   c. The Viewer's 170 account details; and

8. Storing Viewer Interactions 160 for retrieval by the StreamingService API(s) 130.

The core functionalities of the Streaming Service API(s) 130 include,but are not limited to:

1. Retrieving Viewer Interactions 160 for processing;

2. Processing Viewer Interactions 160 into Stream Events 140 formattedfor use in the Streaming Service API(s) 130;

3. Sending the Stream Events 140 to the API Data Collector 260 via theStreaming Service API(s) 130.

The primary implementations of the Alternative API Data Sources 270include, but are not limited to:

1. Data received directly from the videogame;

2. Data received from a computer vision and/or an artificialintelligence engine analysis of the game;

3. Data received from third party APIs related to the user's game, theuser, or the Viewers 170.

Populating the Marketplace

FIG. 3 shows an illustrative process view of a user populating theoverlay marketplace with new graphics.

A First User 350 launches the Local Software in step 280. The LocalSoftware may be executed by any type of a Local Computer 230, and it maybe presented as a web page or a local application. The First User 350then uses the Local Software to authenticate with the ServerInfrastructure 100. Credentials are then passed from the Local Softwareto the Server Infrastructure 100, which validates the authenticationattempt.

Once authenticated, the First User 350 chooses to create a new Image instep 300 using the Local Software of step 280. The First User 350 canbegin creating a new Image in step 300 either by selecting an existingImage to modify or uploading a new Image from their Local Computer 230in step 301. After creating the starting Image in step 300, the FirstUser 350 can optionally choose to edit the Image before finalizing theImage Configuration in step 302, which saves a copy of the ImageConfiguration to the Server Infrastructure 100. Editing the Image instep 302 can include changing the underlying graphics or changing thespecific data event(s) with which the Image is associated.

After the Image Configuration has been saved in step 310, the First User350 chooses to publish their Image to the Marketplace in step 340. Thisprompts the Server Infrastructure 100 to generate and save a copy of theMarketplace Listing in step 330, which is then published and accessibleto users searching for new graphics.

Combining Multiple Graphics to Form a Template

FIG. 4 shows an illustrative process view of a user combining multiplegraphics into a graphical template.

A First User 350 launches the Local Software in step 280. The LocalSoftware may be executed by any type of a Local Computer 230, and it maybe presented as a web page or a local application. The First User 350then uses the Local Software in step 280 to authenticate with the ServerInfrastructure 100. Credentials are then passed from the Local Softwareto the Server Infrastructure 100, which validates the authenticationattempt.

Once authenticated, the First User 350 chooses to create a new Templatein step 290. The Template of step 290 is a collection of new and/orexisting Images that are organized into a single graphic. This allows aSecond User 360 to purchase all of the contained Images at once insteadof having to acquire each of the contained Images separately. This alsopermits a First User 350 to organize a collection of Images that form awhole, cohesive design.

The First User 350 starts by selecting an Image to add to the Templatein step 295. They then have the option to edit the Image in step 300prior to saving it within the Template Configuration in step 320, whichsaves a copy of the Template Configuration of step 320 to the ServerInfrastructure 100. Editing the Template Configuration as in step 300caninclude changing the underlying Images or changing the specific dataevent(s) with which one or more Image within the Template is associated.

After the Template Configuration has been saved in step 320, the FirstUser 350 determines whether more Images need to be added to theTemplate. If so, they repeat the process of adding new Images to theTemplate as in step 295, 300, and 320. Once complete, the First User 350chooses to publish their Template to the Marketplace in step 340. Thisprompts the Server Infrastructure 100 to generate and save a copy of theMarketplace Listing in step 330, which is then published and accessibleto users searching for new graphics.

Purchasing an Image or Template for Use in Overlay

FIG. 5 shows an illustrative process view of a user purchasing an Imageor Template for use in a Graphical Overlay.

A Second User 360 launches the Local Software in step 280. The LocalSoftware may be executed by any type of a Local Computer 230, and it maybe presented as a web page or a local application. The First User 350then uses the Local Software in step 280 to authenticate with the ServerInfrastructure 100. Credentials are then passed from the Local Softwarein step 280 to the Server Infrastructure 100, which validates theauthentication attempt.

Once authenticated, the Second User 360 then uses the Local Software tobrowse Marketplace Listings in step 330 for Images or Templates theywant to use in their own Graphical Overlay. When the Second User 360finds an Image or Template they wish to use in step 296, they can chooseto purchase the Image or Template. Purchasing the Image or Templatesaves a Unique Copy of the Image or Template to the Second User's 360account in step 370. The Second User 360 then has the option to edit theImage or Template in step 297, which updates the Unique Copy of theImage Configuration or Template Configuration in their account. Editingthe Image or Template can include changing the underlying graphicsincluded or changing the specific data event(s) with which the Image orTemplate is associated.

Configuring an Overlay

FIG. 6 shows an illustrative process view of a user configuring theirGraphical Overlay.

A Second User 360 launches the Local Software in step 280. The LocalSoftware may be executed by any type of a Local Computer 230, and it maybe presented as a web page or a local application. The First User 350then uses the Local Software as in step 280 to authenticate with theServer Infrastructure 100. Credentials are then passed from the LocalSoftware to the Server Infrastructure 100, which validates theauthentication attempt.

Once authenticated, the Second User 360 then uses the Local Software tocreate a new Graphical Overlay in step 200, which saves a new copy ofthe Overlay Configuration in step 110 in the Server Infrastructure 100.The Second User 360 then selects Images or a Templates to add theGraphical Overlay in step 201. The Second User 360 then has the optionto edit the Image or Template in step 305, which updates the OverlayConfiguration as in step 110 in their account.

In some embodiments, the Second User 360 then associates the Image orTemplate with specific real time event(s) in step 307. In anotherembodiment, the Second User 360 then associates the Image or Templatewith timer(s). In yet another embodiment, the First User 350 has alreadyassociated the Image or Template with specific real-time event(s), sothe Second User 360 either verifies or modifies the existingassociations. Once the Second User 360 makes any of the aforementionedmodifications, the Overlay Configuration is updated in their account asin step 111.

The Second User 360 determines whether the Graphical Overlay is completein step 112. If not, the Second User 360 repeats the process of addingImages or Templates to the Graphical Overlay as in step 201. If so, thefinal Overlay Configuration is saved to the user's account for laterretrieval as in step 110.

Graphical Overlay

FIG. 7 is a non-limiting example of a configured video overlay shown ona display 391, according to some embodiments. In some embodiments,Images and Templates within the Graphical Overlay are configured toappear when the Streaming Service API(s) 130 report specific eventsincluding. The notifications can include, but are not limited to:

-   -   1.A Viewer 170 has followed the Second User 360, meaning they        will receive notifications from the Streaming Service when the        Second User's 360 broadcast is active.    -   2.A Viewer 170 has subscribed to the Second User's 360 channel.        When a Viewer 170 subscribes to a streamer's channel, they pay a        monthly subscription fee in exchange for subscriber-only        privileges, such as access to subscriber-only interactions with        the Second User 360 and their channel, or access to the Second        User's 360 private chat servers or newsletters. The benefits are        configured by the Second User 360, therefore are not limited to        nor required to include the aforementioned benefits.    -   3.A Viewer 170 has donated money to the Second User 360. While        Streaming Services 150 provide the infrastructure for Viewers        170 to subscribe or follow the Second User 360, monetary        donations are usually facilitated by third party services, such        as Streamlabs. The Streaming Service 150 provides a button the        Viewer 170 can select while viewing the Second User's 360        channel to donate money to the Second User 360. The button        either redirects the Viewer 170 to a third-party page where they        are prompted for their credit card information, it provides a        pop-up directly over the video feed where credit card        information can be entered, or it processes the payment by        accessing payment information stored in the Viewer's 170 account        with the Streaming Service 150.

In the non-limiting example illustrated in FIG. 7, a FollowerNotification 390 comprises a predetermined animation and text conveyingthat a Viewer 170, in this case “whitewalkerzzzz”, has followed theSecond User 360. The Donation Notification 400 also comprises apredetermined animation and text conveying that a Viewer 170, in thiscase “John”, has donated, in this case, $95 to the Second User 360. TheSubscription Notification 410 also comprises a predetermined animationand text conveying that a Viewer 170, in this case“gitthezambiescorrrl”, has subscribed to the Second User's 360 channel.

The aforementioned are non-limiting examples of Images being written toa Graphical Overlay image file in response to specific Streaming ServiceAPI 130 data points. Said Graphical Overlay image file will besubsequently retrieved by the Second User's 360 Local Broadcast Software240, where, per the example provided in FIG. 1 and FIG. 2, it will becombined with the Game Signal 220 and optionally the User Signal 210 bythe Video Encoder 190 to produce an encoded video file. In thenon-limiting example illustrated in FIG. 7, the black backgroundrepresents a transparent layer, and the Graphical Overlay will appear asif it is “on top” of the video signals provided by the Game Signal 220and the User Signal 210.

In some embodiments, one or more of the aforementioned examples mightinclude text without an associated Image. In other embodiments, one ormore of the aforementioned examples might include an Image without text.Furthermore, while editing the Graphical Overlay the Second User 360 mayassign the position at which each notification appears. In someembodiments, the program automatically recommends the position for theSecond User 360, which the Second User 360 can adjust. The Second User360 may also change the font, the font colors, the animation included,the duration, transitions, and a wide range of additional configurationoptions to personalize their Graphical Overlay.

First Illustrative Embodiment

FIG. 8 shows a beginning-to-end illustrative process view of thedisclosed methods, wherein the streaming architecture is direct and thevideo overlay is static.

A Second User 360 launches the Local Software in step 280. The LocalSoftware may be executed by any type of a Local Computer 230, and it maybe presented as a web page or a local application. The First User 350then uses the Local Software in step 280 to authenticate with the ServerInfrastructure 100. Credentials are then passed from the Local Softwareto the Server Infrastructure 100, which validates the authenticationattempt.

Once authenticated, the Second User 360 then uses the Local Software toinitiate a connection with the Streaming Service 150. The Second User's360 credentials or API token are passed to the Streaming Service's 150Streaming Server(s) in step 380. The Streaming Server(s) in step 380then reject the attempt or confirm that the connection is valid. If theconnection is rejected, the Server Infrastructure 100 prompts the LocalBroadcast Software 240 to attempt authentication again. If theconnection is valid, the Server Infrastructure 100 retrieves the SecondUser's 360 Overlay Configuration 110, which contains one or moreImage(s) or Template(s) that the Second User 360 obtained from aGraphical Overlay Marketplace 340. The Overlay Configuration 110 is thenused to begin generating the Graphical Overlay image file. Variations inthe generated Graphical Overlay typically consist of animations based ontimers or images that remain static until manually changed by the SecondUser 360. The Graphical Overlay is then generated at regular intervalsfor as long as the Second User's 360 streaming session is active.

The Local Broadcast Software 240 then collects the user's Game Signal220, User Signal 210, and retrieves the generated Graphical Overlay fromthe Server Infrastructure 100. The sources are then encoded by the VideoEncoder 190 and uploaded to the Streaming Service 150 using a StreamingProtocol 180, including but not limited to HLS, FLV, RTMP, RTSP, andDASH, where it is decoded and played for Viewers 170 to consume.

The aforementioned process of encoding the sources to playback repeatsuntil the Second User 360 decides to stop the broadcast. When thebroadcast is stopped, the Local Broadcast Software 240 stops generatingand uploading the encoded video file; it then sends a signal to end thebroadcast, the Server Infrastructure 100 stops generating the GraphicalOverlay, and the Streaming Service 150 marks the Second User's 360stream as inactive.

Second Illustrative Embodiment

FIGS. 9A and 9B show a beginning-to-end illustrative process view of thedisclosed methods, wherein the streaming architecture is direct and thevideo overlay is dynamic.

A Second User 360 launches the Local Software in step 280. The LocalSoftware may be executed by any type of a Local Computer 230, and it maybe presented as a web page or a local application. The First User 350then uses the Local Software in step 280 to authenticate with the ServerInfrastructure 100. Credentials are then passed from the Local Softwareto the Server Infrastructure 100, which validates the authenticationattempt.

Once authenticated, the Second User 360 then uses the Local Software toinitiate a connection with the Streaming Service 150. The Second User's360 credentials or API token are passed to the Streaming Service's 150Streaming Server(s) in step 380. The Streaming Server(s) in step 380then reject the attempt or confirm that the connection is valid. If theconnection is rejected, the Server Infrastructure 100 prompts the LocalBroadcast Software 240 to attempt authentication again. If theconnection is valid, the Server Infrastructure 100 initiates aconnection to the Streaming Service API 130 to begin reading datarelated to the Second User's 360 channel. The Streaming Service API 130then rejects the Server Infrastructure's 100 connection attempt orconfirms that the connection is valid. If the connection is rejected,the Server Infrastructure 100 attempts to initiate the connection to theStreaming Service API 130 again. If the connection is valid, the ServerInfrastructure 100 begins receiving real time data events from theStreaming Service API 130 and retrieves the Second User's 360 OverlayConfiguration 110, which contains one or more Image(s) or Template(s)that the Second User 360 obtained from the Graphical Overlay Marketplaceof step 340. The Overlay Configuration 110 and data from the StreamingService API 130 are then used to begin generating the Graphical Overlayimage file. Variations in the generated Graphical Overlay typicallyconsist of animations, Images or Templates that are configured to appearwhen the Server Infrastructure receives specific data events from theStreaming Service API 130. Variations can also consist of Images thatremain static until manually changed by the Second User 360. TheGraphical Overlay is then generated at regular intervals for as long asthe Second User's 360 streaming session is active.

The Local Broadcast Software 240 then collects the user's Game Signal220, User Signal 210, and retrieves the generated Graphical Overlay fromthe Server Infrastructure 100. The sources are then encoded by the VideoEncoder 190 and uploaded to the Streaming Service 150 using a StreamingProtocol 180, including but not limited to HLS, FLV, RTMP, RTSP, andDASH, where it is decoded and played for Viewers 170 to consume.

As Viewers 270 interact with the Second User's 360 channel, theStreaming Service API 130 records the interactions and converts theminto a data format that can be easily shared with the ServerInfrastructure 100 via the Streaming Service API 130. Interactionsinclude but are not limited to: chat, subscriptions, follows, donations,and miscellaneous purchases.

The aforementioned process of encoding the sources to playback repeatsuntil the Second User 360 decides to stop the broadcast. When thebroadcast is stopped, the Local Broadcast Software 240 stops generatingand uploading the encoded video file; it then sends a signal to end thebroadcast, the Server Infrastructure 100 stops generating the GraphicalOverlay 200, the Streaming Service 150 marks the Second User's 360stream as inactive, and the Streaming Service API stops generating APIdata based on Viewer 170 actions.

Third Illustrative Embodiment

FIGS. 10A and 10B show a beginning-to-end illustrative process view ofthe disclosed methods, wherein the streaming architecture is direct andthe video overlay is dynamic.

A Second User 360 launches the Local Software in step 280. The LocalSoftware may be executed by any type of a Local Computer 230, and it maybe presented as a web page or a local application. The First User 350then uses the Local Software to authenticate with the ServerInfrastructure 100. Credentials are then passed from the Local Softwareto the Server Infrastructure 100, which validates the authenticationattempt.

Once authenticated, the Second User 360 uses the Local Software toconnect one or more Streaming Service 150 to the Server Infrastructure100. The Streaming Service 150 connection(s) are then stored in theSecond User's 360 account for later access via the Multistream Service250.

The Second User 360 then launches the Local Broadcast Software 240 instep 245. The Second User 360 uses the Local Broadcast Software toauthenticate with the Server Infrastructure 100. Credentials are thenpassed from the Local Broadcast Software 240 to the ServerInfrastructure 100, which validates the authentication attempt.

Once authenticated, the Second User 360 initiates connection(s) with theStreaming Service(s) 150. The Second User's 360 credentials or APItokens are passed to the Streaming Server(s) 380 via the MultistreamService 250, and the Streaming Server(s) 380 return an Active Connectionto the Multistream Service 250. Once the connection(s) are returned, theServer Infrastructure 100 initiates the API Data Collector 260 in step265, which initiates and maintains connections with the StreamingService API(s) 130. The API Data Collector 260 then begins reading datarelated to the Second User's 360 channel(s) for each of the StreamingService(s) 150 to which the Second User 360 has active connections. TheStreaming Service API(s) 130 then reject the API Data Collector's 260connection attempts or confirm that the connection(s) are valid. If theconnections are rejected, the API Data Collector 260 attempts toinitiate the connection to the Streaming Service API(s) 130 again. Ifthe connections are valid, the API Data Collector 260 begins receivingreal time data events from the Streaming Service API(s) 130.

The Server Infrastructure 100 then retrieves the Second User's 360Overlay Configuration 110, which contains one or more Image(s) orTemplate(s) that the Second User 360 obtained from a Graphical OverlayMarketplace 340. The Server Infrastructure 100 then uses the OverlayConfiguration 110 and data from the API Data Collector 260 to begingenerating the Graphical Overlay image file. Variations in the generatedGraphical Overlay typically consist of animations, Images or Templatesthat are configured to appear when the Server Infrastructure receivesspecific data events from the API Data Collector 260. Variations canalso consist of Images 300 that remain static until manually changed bythe Second User 360. The Graphical Overlay is then generated at regularintervals for as long as the Second User's 360 streaming session isactive.

In some embodiments, each Graphical Overlay is generated based on APIdata specific to the associated Streaming Service 150. In otherembodiments, data from one or more Streaming Service(s) 150 may be usedto generate a single Graphical Overlay 200 that contains consolidatednotifications from one or more Streaming Service(s) 150.

The Local Broadcast Software 240 then collects the user's Game Signal220, User Signal 210, and retrieves the generated Graphical Overlay fromthe Server Infrastructure 100. The sources are then encoded by the VideoEncoder 190 and uploaded to the Multistream Service using a StreamingProtocol 180, including but not limited to HLS, FLV, RTMP, RTSP, andDASH. The Multistream Service 250 then uploads the file using aStreaming Protocol 180 to each of the active Streaming Service 150connections in the Second User's 360 account. Once uploaded to each ofthe Streaming Service(s) 150, the encoded video file is decoded andplayed for Viewers 170 to consume.

In other embodiments, the Multistream Service 250 decodes the videofile, then uses a Video Encoder 190 to re-encode a copy of the videofile in a manner that is optimized for each of the Streaming Service(s)150 prior to uploading it to the Streaming Service(s) 150 using aStreaming Protocol 180.

As Viewers 270 interact with the Second User's 360 channel(s) on thevarious Streaming Service(s), the Streaming Service API(s) 130 recordthe interactions and convert them into a data format that can be easilyshared with the API Data Collector 260. Interactions include but are notlimited to: chat, subscriptions, follows, donations, and miscellaneouspurchases.

In some embodiments, Alternative API Data Sources 270, data from sourcesother than the Streaming Service API(s) 130, may send data to the APIData Collector of step 260 for use in creating Graphical Overlays.

The aforementioned process of encoding the sources to playback repeatsuntil the Second User 360 decides to stop the broadcast. When thebroadcast is stopped, the Local Broadcast Software 240 stops generatingand uploading the encoded video file; it then sends a signal to end thebroadcast, the Server Infrastructure 100 stops generating the GraphicalOverlay, the Multistream Service 250 stops operation and notifies theStreaming Service(s) 150 to mark the Second User's 360 stream(s) asinactive, the Streaming Service API(s) 130 stop generating data based onViewer 170 actions, and the API Data Collector 260 stops receiving data.

The various steps recited herein are not intended to limit the inventiveaspects of this disclosure to a particular arrangement or embodiment.The various steps, processes, and methods recited herein may bepracticed in any order or arrangement consistent with the disclosure.

1) A system for a virtual marketplace of video overlays for videocontent broadcasting, the system comprising: non-transitory storagemedia configured to store overlay content information and overlayconfiguration information corresponding to one or more video overlays,wherein the overlay content information defines an image and/or audioand the overlay configuration information specifies values for one ormore settings that define application of the image and/or audio tooverlayed video content, wherein the one or more settings that defineapplication of the overlay configuration information to the overlayedvideo content includes one or more settings that specify a real-timeevent trigger defining when the overlay configuration information isapplied to the overlayed video content, wherein the real-time eventtrigger includes a second user's interaction with the overlayed videocontent; one or more processors configured by machine-readableinstructions to: transmit, to client computing platforms associated withusers, information that facilitates presentation of one or more views ofthe virtual marketplace on the client computing platforms, wherein aview of the virtual marketplace includes one or more overlay offers tosell access to the one or more video overlays, wherein the views of thevirtual marketplace include one or more visual representations of theoverlay content information corresponding to the one or more videooverlays different video overlays to enable inspection of the one ormore video overlays and acceptance of individual ones of the one or moreoverlay offers; receive an acceptance of one or more overlay offers fromthe client computing platforms associated with the users; and responsiveto reception of an acceptance of one or more accepted overlay offersfrom a first client computing platforms associated with a first user,provide the first client computing platform associated with the firstuser access to corresponding accepted video overlays so that the firstclient computing platform is enabled to generate generated video contentthat includes the image and/or audio defined by the overlay contentinformation corresponding to the one or more accepted video overlaysapplied to the overlayed video content in accordance with the overlayconfiguration information corresponding to the one or more acceptedvideo overlays. 2) The system of claim 1, wherein the image of a videooverlay is applied to the overlayed video content as a filter. 3) Thesystem of claim 1, wherein the video content includes image and/or audioinformation captured by the client computing platforms. 4) The system ofclaim 1, wherein the one or more settings that define application of theimage and/or audio of the one or more video overlays to overlayed videocontent further includes one or more settings that specify positions ofthe image applied to the overlayed video content and one or moresettings that specify a duration of the image and/or audio to theoverlayed video content. 5) (canceled) 6) The system of claim 1, whereinusers can present overlay offers to another user through the virtualmarketplace, wherein the one or more processors are further configuredby machine-readable instructions to: receive uploads of overlay contentinformation for one or more video overlays from client computingplatforms associated with users to the virtual marketplace includingoverlay offers to sell access to one or more video overlays. 7) Thesystem of claim 1, wherein the overlay configuration information for thegiven video overlay can be modified by a user via the client computingplatforms. 8) The system of claim 1, wherein the image and/or audiodefined by the overlay content information is applied to the overlayedvideo content by the one or more processors further configured bymachine-readable instructions to: receive the video content from theclient computing platforms; apply the image and/or audio defined by theoverlay content information to the overlayed video content in accordancewith the overlay configuration information; and transmit the generatedvideo content to the client computing platforms. 9) A system forapplying video overlays from a virtual marketplace to video content forbroadcasting, wherein the virtual marketplace includes overlay contentinformation for one or more video overlays that define an image and/oraudio corresponding to the one or more video overlays and overlayconfiguration information that specifies values for one or more settingsthat define application of the overlay content information correspondingto one or more video overlays to overlayed video content, wherein theone or more settings that define application of the overlayconfiguration information to the overlayed video content includes one ormore settings that specify a real-time event trigger defining when theoverlay configuration information is applied to the overlayed videocontent, wherein the real-time event trigger includes a second user'sinteraction with the overlayed video content, the system comprising: oneor more processors configured by machine-readable instructions to:receive, from a first server associated with the virtual marketplace,information that facilitates presentation of views of the virtualmarketplace on client computing platforms associated with users, whereina view of the virtual marketplace includes one or more overlay offers tosell access to the one or more video overlays, wherein the views of themarketplace includes one or more visual representations of images of theone or more video overlays to enable inspection of the one or more videooverlays and acceptance of individual ones of the overlay offers; andtransmit, to the first server, an acceptance of one or more acceptedoverlay offers from the client computing platforms associated with theusers such that responsive to reception of the acceptance of the one ormore overlay offers from the client computing platforms associated withthe users, obtain access to one or more accepted video overlayscorresponding to the one or more accepted overlay offers so thatindividual client computing platforms of the client computing platformsare enabled to generate generated video content that includes the imageand/or audio defined by the overlay content information of the one ormore accepted video overlays applied to the video content in accordancewith the overlay configuration information for the one or more acceptedvideo overlays, wherein the generated video content is encoded prior toa transmission to a third server for broadcasting. 10) The system ofclaim 9, wherein the video content is transmitted to a second serverassociated with the virtual marketplace to generate the generated videocontent that includes the image and/or audio defined by the overlaycontent information of the one or more video overlays applied to theoverlayed video content in accordance with the overlay configurationinformation for the one or more video overlays; and the generated videocontent is received from the second server prior to the encoding of thegenerated video content for the transmission to the third server forbroadcasting. 11) The system of claim 9, wherein the image of the one ormore video overlays is applied to video content as a filter. 12) Thesystem of claim 9, wherein the video content includes image and/or audioinformation captured by the client computing platforms. 13) The systemof claim 9, wherein the one or more settings that define application ofthe image and/or audio of the given video overlay to overlayed videocontent further includes one or more settings that specify positions ofthe image of the given video overlay applied to overlayed video contentand one or more setting that specify a duration of the image and/oraudio of the video overlay applied to overlayed video content. 14) Thesystem of claim 13, wherein the real-time event triggers includeinteractions with the generated video content from the third server. 15)The system of claim 9, wherein the overlay configuration information forthe one or more video overlays can be modified by a user via theindividual client computing platforms. 16) The system of claim 10,wherein the second server used to generate the generated video contentincludes one or more processors configured by machine-readableinstructions to: receive the video content from the individual clientcomputing platforms; apply the image and/or audio defined by the overlaycontent information of the one or more accepted video overlays to thevideo content in accordance with the overlay configuration informationfor the given video overlay to the video content; and transmit generatedvideo content to the individual client computing platforms. 17) Thesystem of claim 1, wherein the real-time event trigger corresponds toone or more of a chat notification, a subscription notification, adonation notification, or a new follower notification. 18) The system ofclaim 9, wherein the real-time event trigger corresponds to one or moreof a chat notification, a subscription notification, a donationnotification, or a new follower notification.